Description

Fixes #2004.

select_related(...) requests a LEFT OUTER JOIN, but .values() and .values_list() silently dropped it. When an annotation, filter or ordering referenced the joined table — e.g. a RawSQL term used for something the ORM can't express directly, like a cast — the generated SQL referenced the related alias with no matching join, so the query crashed:

q = (Book.all().select_related("author")
       .annotate(custom=RawSQL("book__author.age * 2"))
       .order_by("custom"))

q.sql()                              # has the JOIN
q.values_list("id", flat=True).sql()
# SELECT "id" FROM "book" ORDER BY book__author.age * 2 ASC   -- JOIN gone
await q.values_list("id", flat=True)
# OperationalError: no such column: book__author.age

The regular QuerySet path joins correctly (QuerySet._make_query calls _join_select_related); only the value-query path was missing it.

Fix

Thread the requested select_related lookups through to ValuesQuery / ValuesListQuery and register the joins in their _make_query. A small AwaitableQuery._join_select_related_tables() helper adds only the joins (not the related columns, which the projection does not select), so:

• the related alias resolves and the query runs;
• .values() / .values_list() output shape is unchanged (no extra columns);
• queries without select_related are unaffected (no spurious joins).

Tests

Added test_select_related_join_preserved_in_values and ..._in_values_list to tests/test_values.py. Both fail on develop with OperationalError: no such column and pass with the fix. The full tests/test_values.py and tests/test_queryset.py suites pass, and ruff/mypy are clean.